FAQ: Learning Clean Architecture and Layered Architectures
Learning Clean Architecture and Layered Architectures
[00:00:00]
And the layered architecture. And the onion architecture. And there's all sorts of names for it. Layered is actually a little bit different, but it's the same thing. So yeah, we're going to get our first dose of this in the best practice phase of development.
Phases of craftship rather, we're going to get our first taste of this there when we need to decouple from the database because we're going to need to just test that works. We're going to integration test that a little bit and we could also just move some things around. So that's where we're just going to start to carve out a more of a layered architecture.
But then we're going to take it a little bit further in pattern first, which is where we then insert that adapter layer. And that's when it becomes the hexagonal or the clean architecture, [00:01:00] is when there's a decoupling from core code to infrastructure code. So that's how we're going to get into that.
And then from that. Architecture, we're going to do a lot of different work with testing and with building features and just exploring that particular layout in the responsibility first phase of craftship. I don't think we were really going to do a whole lot more with that other than by introducing an event based architecture.
How I'm going to learn clean architecture and ports and adapters and onion and all that stuff. Just go through the phases of the craftship best practice first is when we're going to get our first dose, but we're going to do the majority of that work in the pattern first phase.